fix(packed): restore optional peer boundaries - #280

Summary

• keep the packed tool/after request-context probe inside native hook output instead of an invalid Agent.Result.value
• keep agent-bundle runtime JS and declarations importable without the optional runtime peer
• split React rendering from event envelope projection so lifecycle replay does not make the public API eagerly require React
• improve packed failure diagnostics and add a patch changeset

Root cause

• feat(runtime): expose typed request context to operation handlers and the test harness (#223) #273 added { actor } to the shared event fixture's result value, but projectEventDocument intentionally accepts only native hook fields (outcome, reason, updatedInput)
• feat(state): kernel budgets and lifetime visibility (#233 items 3-4) #268 imported state budget defaults as a runtime value from the optional runtime peer; feat(routes): execute conventional context providers in generated request scopes (#95 remainder) #255 also leaked its invocation type into the packed declaration closure
• feat(dev): semantic lifecycle replay (#105 stage 3) #279, which landed while this branch was being prepared, made lifecycle replay import the React-backed event renderer from the public API path

Test plan

• pnpm test:packed (9 files; 23 passed, 1 skipped)
• pnpm typecheck
• pnpm lint (0 errors, 0 warnings)
• event projection + lifecycle replay unit tests (8 passed)
• route-unit lifecycle + render tests (19 passed)
• packaged lifecycle replay dev-server integration (1 passed)